Discussed with @dmytroye ,
External tracker service that subscribes to DATA_CAMERA and publishes tracks in a scene on DATA_SCENE should also subscribe to DATA_EXTERNAL. However if this is not in the current scope of external tracker service , then I suggest completely disabling scene hierarchy in controller's analytics only mode.

Points to consider:

• Controller in analytics only mode can not fuse tracks from child with tracks in the scene. However it can republish events that are rightly transformed. But they don't hold any significance without tracks.
• In the else part of subscriptions in local child scene and remote child scene, subscribing to DATA_SCENE will yield in republishing the same tracks got from the child scene under the same topic. Redundant.

@dmytroye Refer to https://github.com/open-edge-platform/scenescape/blob/main/docs/user-guide/building-a-scene/how-to-use-sensor-types.md#steps-to-integrate-environmental-and-attribute-sensors. Please check if the behavior is not changed for these sensor types.
I believe attribute persistence is an attribute of moving object which is associated by the tracker. Please verify.

@dmytroye Refer to https://github.com/open-edge-platform/scenescape/blob/main/docs/user-guide/building-a-scene/how-to-use-sensor-types.md#steps-to-integrate-environmental-and-attribute-sensors. Please check if the behavior is not changed for these sensor types. I believe attribute persistence is an attribute of moving object which is associated by the tracker. Please verify.

In the default mode data from sensors also visible on data/scene topic. But in Analytics only mode is not visible due to all data is generated from K6 script (mimics separate tracker service). Even if sensor data will be published it will be immediately overwritten by new message from tracker (or k6 in case of simulation). Events are publishing correctly in both modes.

Discussed with @dmytroye , External tracker service that subscribes to DATA_CAMERA and publishes tracks in a scene on DATA_SCENE should also subscribe to DATA_EXTERNAL. However if this is not in the current scope of external tracker service , then I suggest completely disabling scene hierarchy in controller's analytics only mode.

Points to consider:

• Controller in analytics only mode can not fuse tracks from child with tracks in the scene. However it can republish events that are rightly transformed. But they don't hold any significance without tracks.
• In the else part of subscriptions in local child scene and remote child scene, subscribing to DATA_SCENE will yield in republishing the same tracks got from the child scene under the same topic. Redundant.

@sarthakdeva-intel Scene hierarchy in controller's analytics only mode disabled for objects and events republish.